You can use the N4 Decking History view to monitor vessel discharge decking requests sent to an N4 XD server or to the XPS server when the N4 XD server(s) are not available. The Decking History view enables you to verify that the XD requests are being processed, who processed them, and to see how long the decking requests are taking.
The following table details the decking types recorded in the Decking History view for the Scaled N4 XD service scenarios, including exception and failover scenarios, the component where the XD request was sent, and the result.
|
Scenario |
Action taken |
Component |
Decking Type |
Result |
|---|---|---|---|---|
|
ACTIVE N4 XD server(s) are available and the N4 setting ARGOBENTO002 is set to XPS_SERVER_WITH_XD. |
N4 sends the vessel discharge decking Bento request to an ACTIVE N4 XD server. |
N4 XD server |
XD Vessel Discharge |
Discharged container is assigned to a valid yard position. |
|
No ACTIVE N4 XD server(s) are available and the N4 setting ARGOBENTO002 is set to XPS_SERVER_WITH_XD. |
Since there are no available N4 XD servers, N4 sends the vessel discharge decking Bento request to the XPS server’s XD service. |
XPS |
XD Vessel Discharge |
Discharged container is assigned to a valid yard position. |
|
ACTIVE N4 XD server(s) are available and the N4 setting ARGOBENTO002 is set to XPS_SERVER_WITH_XD, but N4 was not able to connect to the ACTIVE N4 XD server. |
N4 sets the N4 XD server node status to INACTIVE and tries for another ACTIVE N4 XD server, if available, or the XPS server. |
N4 XD server |
XD Vessel Discharge - Connection Failure |
N/A - retries other N4 XD servers, if available, or the XPS server. |
|
N4 did not receive a response from the N4 XD server within the time specified in N4 setting ARGOXPS006. |
To avoid further delay, N4 assigns a FLD (failed to deck) position to be included in the vessel discharge decking Bento request to XPS. |
N4 XD server |
XD Vessel Discharge - Timeout |
Discharge container fails to deck (FLD). |
|
After attempts to use the N4 XD server(s) failed, N4 was not able to connect the XPS server. |
N4 assigns a FLD position and sends the vessel discharge decking Bento request with the FLD position back to XPS. |
XPS |
XD Vessel Discharge - Connection Failure |
Discharge container fails to deck (FLD). |
|
After attempts to use the N4 XD server(s) failed, N4 did not receive a response from the XPS server within the time specified in ARGOXPS006. |
N4 assigns a FLD position and sends the vessel discharge decking Bento request with the FLD position to XPS. |
XPS |
XD Vessel Discharge - Timeout |
Discharge container fails to deck (FLD). |
Regardless of the case, N4 sends XPS either a valid yard position or a FLD position. In addition, for all cases, N4 generates a log entry that states if any ACTIVE N4 XD servers were available or not, identifies the origin of the request (the N4 node), and identifies the N4 XD server or XPS server that processed it.
For more information, see Decking History view and Decking Types.